Additional documents of interest
- Successful Business Continuity - Part 1 - Users and Groups
-
This article was published in the April 2005 issue of
AIX Update magazine
and discusses system administration needs and requirements oriented
around users and groups. The overall emphasis of this series of
articles is for implementation of enterprise wide unique identifiers
for a variety of parameters, such as user names, group names, UID and
GID numbers.
- Successful Business Continuity - Part 2 - Machine and Host Names
-
This article was published in the May 2005 issue of
AIX Update magazine
and discusses naming structures for machines, systems, adapters, and
aliases. The overall emphasis of this series of articles is for
implementation of enterprise wide unique identifiers for a variety of
parameters.
- Successful Business Continuity - Part 3 - Volume Names
-
This article was published in the December 2005 issue of
AIX Update magazine
and discusses naming structures for volume groups, logical volumes, log
logical volumes, directory mount points, etc. The overall emphasis of
this series of articles is for implementation of enterprise wide unique
identifiers for a variety of parameters.
- Successful Business Continuity - Part 4 - MQ Series, Startup/Shutdown Scripts, Error Processing
-
This article was published in the April 2006 issue of
AIX Update magazine
and discusses how to implement AIX in an environment dedicated to
business continuity. The topic of this article is the assignment of MQ
Series queue names and aliases, resource group startup and shutdown
script names (Application startup/shutdown script names), error logging,
and error notification.
- Successful Business Continuity - Part 5 - Miscellaneous topics
-
This article was published in the August 2006 issue of
AIX Update magazine
and discusses how to implement AIX in an environment dedicated to
business continuity. A variety of topics is discussed in this article
including automated documentation generation and management.
- Automated Microcode Management System
-
One of the most difficult administration tasks in an AIX environment is
attempting to keep the firmware and microcode up-to-date. Mt Xia has
devised an automated method of gathering the Microcode information,
determining which microcode needs to be updated, generating reports, and
uploading the required microcode updates to each individual system.
- Calculating the size of a Virtual Processor
-
This document describes the algorithms used to calculate the size of a
virtual processor when using shared processors in an LPAR. The IBM
documentation describes how to calculate CPU utilization, NOT how to
size for configuration, this document clarifies this process. A
description of the HMC input fields for the processor tab is included.
- Basics of Partition Load Manager Setup
-
This presentation was provided by Ron Barker from IBM regarding the PLM Basic
setup.
- ppt
- pdf
|
 |
 |
 |
 |
Resource Group Name Standards
The concept of Resource Group is used here in a
larger scope than it is used in HACMP. In Mt Xia's environment, a resource
group is any logical collection of resources, this may include disk,
I/O, users, applications, etc. A resource group should be
viewed as being independent from any machine or data center.
The resource group name is used as the basis of all other naming
structures for all entities whether or not they are controlled by HACMP.
The resource group name shall be an enterprise wide unique value in
order to eliminate conflicts during manual, automated, or disaster
recovery failovers.
When designing any new system, the first step is to determine the
resource group name(s). The names of volume groups, logical volumes,
mount points, major numbers, WLM classes, etc, are all derived from the
resource group name(s).
The resource group name shall consist of exactly 8 characters
with the following structure:
ApplicationCode + Environment + Function + Company + Sequence ID
3 char + 1 char + 1 char + 2 char + 1 char
The detailed information for each component of the resource group
name is described below:
RG Name
Component
|
Number of
Characters
|
Values
|
|
Application Code
|
3
|
atl = Atlas
ega = EGATE
nim = NIM
ora = Oracle
tps = Maximo
vio = Virtual I/O
|
|
Environment
|
1
|
a = acceptance
a = pre-production
d = test/development
p = production
t = test
x = disaster recovery
x = pre-production
|
|
Function
|
1
|
a = application
c = combination/multi-purpose
d = database
m = management
u = utility
|
|
Company
|
2
|
mx = Mt Xia
mi = Mt Xia - India
ib = IBM
tw = Time Warner
cg = Capgemini
|
|
Sequence ID
|
1
|
0-9,A-Z,a-z
|
Examples of Resource Group (RG) names:
- egapdmx0
-
EGATE Production database RG for Mt Xia, first instance
- egapdmx1
-
EGATE Production database RG for Mt Xia, second instance
- nimpuib0
-
Network Information Manager production utility RG for IBM, first instance
- nimpuib1
-
Network Information Manager production utility RG for IBM, second instance
- viopuib1
-
Virtual I/O production utility RG for IBM, first instance
- viopuib2
-
Virtual I/O production utility RG for IBM, second instance
- viopuib3
-
Virtual I/O production utility RG for IBM, third instance
- viopuib4
-
Virtual I/O production utility RG for IBM, fourth instance
- vioauib1
-
Virtual I/O acceptance utility RG for IBM, first instance
- vioauib2
-
Virtual I/O acceptance utility RG for IBM, second instance
- vioauib3
-
Virtual I/O acceptance utility RG for IBM, third instance
- vioauib4
-
Virtual I/O acceptance utility RG for IBM, fourth instance
- tpspdmx0
-
Maximo production database RG for Mt Xia, first instance
- tpspdmx1
-
Maximo production database RG for Mt Xia, second instance
|
 |
 |
 |
 |
|
|
